Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

updates signature / documents for timeoutWith #1902

Merged
merged 2 commits into from
Aug 31, 2016

Conversation

kwonoj
Copy link
Member

@kwonoj kwonoj commented Aug 24, 2016

Description:
This PR updates signature of timeoutWith to accept withObservable as ObservableInput, as internal implementation already able to support it via utilizing subscribeToResult. In addition to those, updated migration document to list timeout operator split.

Related issue (if exists):

@coveralls
Copy link

Coverage Status

Coverage remained the same at 97.115% when pulling c0b78bc on kwonoj:chore-timeoutwith into 80b817f on ReactiveX:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 97.115% when pulling 3ea1b75 on kwonoj:chore-timeoutwith into 80b817f on ReactiveX:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 97.115% when pulling 0c00ed0 on kwonoj:chore-timeoutwith into cb40e92 on ReactiveX:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 97.115% when pulling cb2a618 on kwonoj:chore-timeoutwith into 990594b on ReactiveX:master.

@jayphelps
Copy link
Member

LGTM, please rebase.

- update signature to accept withObservable as ObservableInput, to align with internal

implementation
@coveralls
Copy link

coveralls commented Aug 31, 2016

Coverage Status

Coverage remained the same at 97.115% when pulling 3ea1b75 on kwonoj:chore-timeoutwith into 80b817f on ReactiveX:master.

@kwonoj kwonoj merged commit 74333eb into ReactiveX:master Aug 31, 2016
@kwonoj kwonoj deleted the chore-timeoutwith branch August 31, 2016 19:11
@lock
Copy link

lock bot commented Jun 6, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants